Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix exception: heightOfLastBlock must match chainHeight #6018

Merged
merged 1 commit into from Feb 7, 2022
Merged

Fix exception: heightOfLastBlock must match chainHeight #6018

merged 1 commit into from Feb 7, 2022

Conversation

ghost
Copy link

@ghost ghost commented Feb 2, 2022

Fixes #6016

If DaoStateStore gets out of sync with BsqBlocks, Bisq ends up in a cycle where it cannot start up.

This PR handles the issue by:

  • clearing the DAO state to be rebuilt from resources on the next startup
  • triggering a popup informing the user that a restart is needed.

image


To reproduce the "heightOfLastBlock must match chainHeight" problem, replace your DaoStateStore file with one from a different instance of Bisq that has not been started in a while, so that it is out of sync with your BsqBlocks.

Copy link
Contributor

@ripcurlx ripcurlx left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

utACK - code changes are looking fine 👍

@ripcurlx ripcurlx added this to the v1.8.3 milestone Feb 7, 2022
@ripcurlx ripcurlx merged commit ee33fee into bisq-network:master Feb 7, 2022
@ghost ghost deleted the fix_OutOfSyncBsqBlocks branch October 18, 2023 16:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

error when opening the Bisq application: heightOfLastBlock must match chainHeight
1 participant